Method and system for efficient management of a communication system

ABSTRACT

A method that incorporates the subject disclosure may include, for example, identifying, by a network device comprising a processor, a bearer path through a communication network for carrying internet protocol packets associated with a calling session between a first mobile device and a second mobile device and activating, by the network device, a bridging bearer path at a nearest network element to generate a direct tunnel for carrying the internet protocol packets associated with the calling session and to modify the bearer path to a shortest bearer path, where the nearest network element comprises a network element that is communicatively coupled to both the first mobile device and the second mobile device and that is closest to the first mobile device and the second mobile device. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of and claims priority to U.S.application Ser. No. 14/085,781, filed Nov. 20, 2013. The contents ofthe foregoing are hereby incorporated by reference into this applicationas if set forth herein in full.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a method and system for efficientmanagement of a communication system.

BACKGROUND

Communication systems, such as a mobile communications system, can beused for providing various services, including voice, video and/or dataservices, and user location information can be important for nextgeneration IP multi-media services provided by telecommunication systemsAs the number of users and their service requirements increase, the loadon the network increases. Infrastructure expansion and improvement canlessen the network load but is costly.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a cellular system forproviding shortest bearer paths for carrying internet protocol packetsduring calling sessions;

FIG. 2 depicts an illustrative embodiment of a method for providingshortest bearer paths for carrying internet protocol packets duringcalling sessions;

FIG. 3 depicts an illustrative embodiment of the cellular system forproviding shortest bearer paths for carrying internet protocol packetsduring calling sessions;

FIG. 4 depicts an illustrative embodiment of a communication device thatcan be used with a communication system for providing shortest bearerpaths for carrying internet protocol packets during calling sessions;and

FIG. 5 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments of a method and system for providing shortest bearer pathsfor carrying internet protocol packets during calling sessions. Theexemplary embodiments can be used to manage network routing options forUser Equipment (UE), or mobile communication devices operating at a LongTerm Evolution (LTE) network. The method can be useful for efficientmanagement and routing of voice-over-internet protocol (VoIP) calls onan LTE communication network, also called voice-over-LTE (VoLTE). Themethod also be useful for routing non-voice data packets betweenend-user devices, such as video data associated with video callingsessions.

In the general solution for VoLTE, the LTE communication network mustselect and manage a real-time transport protocol (RTP) bearer path tocarry IP data packets between two mobile devices engaged a VoLTE callingsession. The data packets for the calling session generally must berouted via a network element that hosts a transcoder pool. This networkelement is typically high up in the hierarchy of the LTE network, wellabove the hierarchical level of the mobile devices. Therefore, even incases when the two mobile devices that are engaging in the callingsession are physically next to each other, the RTP bearer path for theIP data packets can be relatively long. As a result, users of thecommunication system experience longer delay to hear the other party.Also, network resources are required to support the entire RTP bearerpath, which reduces the operating efficiency of the system, whileincreasing demand on network resources. By shortening the RTP bearerpath, user experiences can improve, while operator capital expenditureand operation expense can be reduced.

One embodiment of the subject disclosure is a mobility management entitydevice, comprising a processor; and a memory that stores executableinstructions that, when executed by the processor, can facilitateperformance of operations, including receiving a calling messageindicating a calling session between a first mobile device and a secondmobile device. The executable instructions can also facilitateperformance of operations for retrieving first network informationassociated with the first mobile device and second network informationassociated with the second mobile device according to the callingmessage. The executable instructions can further facilitate performanceof operations for identifying a bearer path through a communicationnetwork for carrying internet protocol packets associated with thecalling session according to the first network information and thesecond network information. The executable instructions can alsofacilitate performance of operations for determining whether the callingsession qualifies for bearer path shortening according to the firstnetwork information and the second network information, where theshortening reduces a number of required elements in the bearer path. Theexecutable instructions can further facilitate performance of operationsfor determining a network element that is communicatively coupled toboth the first mobile device and the second mobile device and that isclosest to the first mobile device and the second mobile device toidentify a nearest network element according to the calling sessionqualifying for bearer path shortening. The executable instructions canfacilitate performance of operations for determining if nearest networkelement comprises a bridging bearer path and, in turn, for activatingthe bridging bearer path to generate a direct tunnel for carrying theinternet protocol packets associated with the calling session and tomodify the bearer path to a shortest bearer path.

One embodiment of the subject disclosure includes a machine-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprisingidentifying a bearer path through a communication network for carryinginternet protocol packets associated with a calling session between afirst mobile device and a second mobile device. The executableinstructions can facilitate performance of operations for determiningwhether the calling session qualifies for bearer path shorteningaccording to network information associated with the first mobile deviceand the second mobile device. The executable instructions can facilitateperformance of operations for identifying a network element that iscommunicatively coupled to both the first mobile device and the secondmobile device and that is closest to the first mobile device and thesecond mobile device to identify a nearest network element according tothe calling session qualifying for bearer path shortening. Theexecutable instructions can facilitate performance of operations foractivating a bridging bearer path at the nearest network element togenerate a direct tunnel at the nearest network element for carrying theinternet protocol packets associated with the calling session and tomodify the bearer path to a shortest bearer path.

One embodiment of the subject disclosure can include a method,comprising identifying, by a network device comprising a processor, abearer path through a communication network for carrying internetprotocol packets associated with a calling session between a firstmobile device and a second mobile device and activating, by the networkdevice, a bridging bearer path at a nearest network element to generatea direct tunnel for carrying the internet protocol packets associatedwith the calling session and to modify the bearer path to a shortestbearer path, wherein the nearest network element comprises a networkelement that is communicatively coupled to both the first mobile deviceand the second mobile device and that is closest to the first mobiledevice and the second mobile device.

FIG. 1 depicts an illustrative embodiment of a system 100 for providingshortest bearer paths for carrying internet protocol packets duringcalling sessions. The system 100 provides shortest RTP bearer paths forcalling sessions over an LTE network, such as, VoLTE to VoLTE calls. Byselecting and activating shortest RTP bearer paths, delay times can bereduced to thereby reduce “mouth-to-ear” latency for mobile users duringVoLTE to VoLTE calls. In addition, selection and usage of the shortestRTP bearer path also improves VoLTE network overall resource efficiency.

In FIG. 1, a mobile communication system 100 is illustrated that canprovide communication services, including voice, video and/or dataservices to mobile devices, such mobile communication devices, or enduser devices 110 a-e. System 100 can enable communication services overa number of different networks, such as between end user devices(UE1-UE5) 110 a-e. The end user devices 110 a-e can be a number ofdifferent types of devices that are capable of voice, video and/or datacommunications, including a mobile device (e.g., a smartphone), apersonal computer, a set top box, and so forth. In one or moreembodiments, the end user devices 110 a-e can be smart mobilecommunication devices that can include cellular transceivers forcommunicating with a cellular system, such as a Long-Term Evolution(LTE) system 105. The end user devices 110 a-e can also include shortdistance wireless transceivers, such as Wi-Fi transmitters, forcommunicating with a wireless local area network (LAN) 125.

System 100 can include a primary Long-Term Evolution (LTE) Radio AccessTechnology (RAT) network, such as E-UTRAN, for providing wirelessconnectivity to eNodeB nodes 140 a-b. E-UTRAN can utilize a number ofinterfaces including Iu, Uu, Iub and/or Iur. The system 100 can alsoinclude one or more secondary RAT networks, such as a Universal MobileTelecommunications System (UMTS), a Global System for Communications(GSM) network, Evolution Data Only (EVDO) network, or a Code DivisionMultiple Access (CDMA) network. In one or more embodiments, UMTS canfacilitate communications between base stations (e.g., Ater and Abisinterfaces) and base station controllers (e.g., A interfaces). Thesystem 100 can use the second RAT networks for accessing the core LTEnetwork 105 directly, while bypassing the eNodeB devices 140 a-b. Thesystem 100 can implement a fallback method whereby, if the primaryRAT/eNodeB access is down or impaired, then the system 100 can fall backto allowing system access via the secondary RAT capabilities.

The system 100 can further include a Mobility Management Entity (MME)160. Other components not shown can also be utilized for providingcommunication services to end user devices 110 a-e, such as a MobileSwitching Center (MSC) which can facilitate routing voice calls andShort-Message Service (SMS), as well as other services (e.g., conferencecalls, FAX and circuit switched data) via setting up and releasingend-to-end connections, handling mobility and hand-over requirementsduring the communications, and/or performing charging and real timepre-paid account monitoring.

In one or more embodiments, E-UTRAN can be the air interface for an LTEupgrade path for mobile networks according to the 3GPP specification.E-UTRAN can include one or more eNodeB nodes 140 a-b on the network thatare connected to each other such as via X2 interfaces 130 and which arefurther connectable to the packet-switch core network 105 via an S1interface. For example, E-UTRAN can use various communication techniquesincluding orthogonal frequency-division multiplexing (01-DM),multiple-input multiple-output (MIMO) antenna technology depending onthe capabilities of the terminal, and beam forming for downlink tosupport more users, higher data rates and lower processing powerrequired on each handset.

In one or more embodiments, a Home Subscriber Server (HSS) 155 can beprovided that is a central database that contains user-related andsubscription-related information. The functions of the HSS 155 includefunctionalities such as mobility management, call and sessionestablishment support, user authentication and access authorization. Inone embodiment, the HSS 155 can manage subscription-related informationin real time, for multi-access and multi-domain offerings in an all-IPenvironment. The HSS 155 can be based on Home Location Register (HLR)and Authentication Center (AuC).

In one or more embodiments, MME 160 can perform the function of acontrol-node. For example, the MME 160 can perform functions such asidle mode tracking and paging procedure including retransmissions. TheMME 160 can also choose a serving gateway for the end user device 110 asuch as at the initial attach and at time of intra-LTE handoverinvolving node relocation. MME 160 and HHS 155 can be accessed when theend-user device 110 a attempts to re-register to user E-UTRAN 120 toaccess the core network 105.

In one or more embodiments, a Serving Gateway (S-GW) 170 can route andforward user data packets, while also acting as the mobility anchoredfor the user plane during inter-eNodeB node 140 a-b handovers and as theanchored gateway for mobility between LTE and other 3GPP technologies(e.g., terminating S4 interface and relaying the traffic between 2G/3Gsystems and P-GW 175). For idle state UEs 110 a, the S-GW 170 canterminate the downlink data path and can trigger paging when downlinkdata arrives for the UE 110 a. The S-GW 170 can manage and can store UE110 a contexts, e.g. parameters of the IP bearer service, networkinternal routing information.

In one or more embodiments, a PDN Gateway (P-GW) 175 can provideconnectivity from a UE 110 a to external packet data networks by beingthe point of exit and entry of traffic for the UE 110 a. UE 110 a canhave simultaneous connectivity with more than one P-GW 175 for accessingmultiple PDNs. The P-GW 175 can perform policy enforcement, packetfiltering for each user, charging support, lawful interception and/orpacket screening. The P-GW 175 can also act as the anchored device formobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2(CDMA 1× and EvDO).

In one or more embodiments, a Policy Control Resource Function (PCRF)180 can be provided. For example, the PCRF 180 can be a software nodedesignated in real-time to determine policy rules. As a policy tool, thePCRF 180 can operate at the network core and can access subscriberdatabases and other specialized functions, such as a charging system, ina centralized manner. The PCRF 180 can aggregate information to and fromthe network, operational support systems, and other sources (such asportals) in real time, supporting the creation of rules and thenautomatically making policy decisions for each subscriber active on thenetwork. The PCRF 180 can provide a network agnostic solution (e.g.,wire line and/or wireless) and can be integrated with differentplatforms like billing, rating, charging, and subscriber database or canalso be deployed as a standalone entity. The functions performed by thePCRF 180 can be any variety of functions, such as computer implementedsteps in a process or algorithm associated with operation of a mobilecommunications network.

In one or more embodiments, system 100 can enable smart mobile devices(UE1-UE5) 110 a-e that include multiple technologies (e.g., cellulartransceivers and Wi-Fi transceivers) to engage in calling sessions,where a shortest bearer path can be provided carrying internet protocolpackets between end user devices 110 a-e. The exemplary embodiments canbe used to manage network routing options for end user devices 110 a-eand can be useful for efficient management and routing ofvoice-over-internet protocol (VoIP) calls.

In one or more embodiments, the method targets calling sessions betweenuser devices 110 a-e, where the calling sessions can be voice-over-LTE(VoLTE). The calling sessions can involve user devices 110 a-e that aremembers of one MME group service area. That is, both the calling and thecalled parties can be using user devices 110 a-e that are serviced by asingle MME 160. In one or more embodiments, the user devices 110 a-ehave GPS or location functions and can also determine or estimate itsspeed of motion.

In one or more embodiments, a calling end user device 110 a can send acalling message to the MME 160 to alert the MME 160 that a callingsession has been requested with a called device 110 b. For example, acalling end user device 110 a can send a session invitation protocol(SIP) INVITE message to the communication system 100. The SIP INVITE canbe forwarded to the MME 160 by the eNodeB 140 a. The MME 160 can analyzethe calling message to determine the identities of the calling userdevice 140 a and the called user device 140 b.

In one or more embodiments, the MME 160 can retrieve network informationassociated with the calling and called end user devices 110 a-b. The MME160 can determine which whether both devices 110 a-b are part of a groupthat is serviced by the MME 160. Alternatively, the MME 160 candetermine whether both devices 110 a-b are part of the same service areafor the P-GW 175. In one embodiment, this is the minimum requirement forthe method to select and enable the shortest RTP bearer path. In anotherembodiment, the MME 160 can verify that the both of the end user devices110 a-b are registered to the service provider of the communicationsystem 100 as a prerequisite for using the shortest RTP bearer path. Inanother embodiment, the MME 160 can determine from the networkinformation that both of the end user devices 110 a-b are intended orare likely to remain in the same MME group and/or P-GW group. If bothdevices 110 a-b are not in the same MME group and/or P-GW group, are notgoing to remain in the same MME group and/or P-GW group, or are notregistered to the same service provider, then the MME 160 can processthe call session such that the typical RTP bearer path is used. However,if these limitations are met, then the MME 160 can take advantage of thesignal processing proximity of the two end user devices 110 a-b toshorten the RTP bearer path.

In one or more embodiments, the MME160 can determine if the calling andcalled devices 110 a-b each support a common voice coder-decoder(CODEC). By supporting a common voice CODEC, the end-user devices 110a-b can communicate directly, through a transcoder free bridge via, forexample, an eNobeB node 140 a in a shortened bearer path. If the devices110 a-b do not share a common voice CODEC, then it is necessary to routethe voice data from each of the devices 110 a-b through the entire,typical network path to transcoders. The network transcoders cantranslate/convert the divergent voice data rates to create a commonstandard. For example, if the calling and called devices 110 a-b do notshare a common voice CODEC, then their bearer paths may have to carrythe signals to the Operator's IP Servics 185 to access a transcoder. Bycontrast, if the two devices 110 a-b share a common voice CODEC, thenthe bearer paths can be shortened substantially, perhaps only extendingas far as the eNodeB node 140 a that services the two devices 110 a-b.

In one or more embodiments, the MME 160 can determine if the end-userdevices 110 a-b are stationary or moving. Mobility information can beexchanged during the set-up for the call session. In one embodiment,each end-user device 110 a can track its position according to GPSinformation and determine if the device 110 a is in motion or isstationary. The device 110 a can, for example, compare locationinformation, over time, to determine if the device 110 a is moving and,if so, then to further determine a rate of movement. In one embodiment,the end-user device 110 a can compare a rate of movement against athreshold of movement rate to determine if the movement isconsequential. For example, the end-user device 110 a can move about ina narrow or area, such as if the caller was walking around in arelatively small area. In that case, the end-user device 110 a candetermine that the movement is not sufficiently large so as to cause anychanges to the routing of the call—such as moving from an area coveredby a first eNodeB 140 a to an area covered by a second eNodeB 140 b. Inanother example, the end-user device 140 a can determine that the device140 a is moving through larger area or at a faster rate and might wellleave a first eNodeB 140 a to an area covered by a second eNodeB 140 b.In other embodiments, end-user devices 110 a can use other methods fordetermining movement, such as kinetic energy signals at the device 110 aand/or changes in signal strength. In one embodiment, the MME 160 canuse information regarding the movement and/or stationary nature ofend-user devices 110 a-b engaged in a calling session to conclude ifthese devices are moving and, if so, then if this movement issignificant. If the MME 160 determines that the movement is significant,then the MME 160 can determine that shortest path routing will not beavailable for this calling session.

In one or more embodiments, the MME 160 can first determine the normal,or default, RTP bearer path, without shortening. In the event that theMME 160 is unable to determine a shortened pathway, then this defaultRTP path can be used for carrying the IP data packets.

In one or more embodiments, the MME 160 can determine a nearest networkelement that can support a shortest RTP bearer path, one that is shorterthan the default bearer path. To determine the nearest element, the MME160 can use the network information for the calling and called end userdevices 110 a-b to first determine all of the network elements that arecommunicatively coupled to each of these end user devices 110 a-b. Forexample, where the calling and called devices are UE1 110 a and UE2 110b, these end user devices share network elements eNodeB 140 a, S-GW 170,and P-GW 175. The network element closest to the two calling sessiondevices 110 a-b is eNodeB 140 a, while the network element that isfarthest away, in terms of the signal path, is P-GW 175. In anotherexample, where UE2 110 b and UE3 110 c are the calling session devices,then the MME 160 can determine that the both devices are commonlycoupled to network elements eNodeB 140 a, S-GW 170, and P-GW 175, plusthe wireless local area network (LAN) 125. In this case, the nearestnetwork element can be either the eNodeB node 140 a or the wireless LAN125. However, since the wireless LAN 125 can be utilized to transmitdata between the UE2 110 b and UE3 110 c without use of other systemresources, the MME 160 can prefer the wireless LAN 125 as the nearestnetwork element.

In another example, where UE2 110 b and UE4 110 d are the callingdevices, the MME 160 can determine from network information that the twodevices do not share eNodeB nodes. Rather, UE2 110 b is served by eNodeB140 a while UE4 110 d is served by eNodeB 140 b. In this case, thecommonly coupled elements appear to be S-GW 170 and P-GW 175. However,MME 160 can also determine the X2 interface 130 can serve as a commonlycoupled network element since it is coupled to each end user device 110b and 110 d via the eNodeB nodes 140 a-b. The X2 interface is thenearest network element. In yet another example, UE2 110 b can engage ina calling session with UE5 110 e. In this case the nearest networkelements are S-GW 170 and P-GW 175, since the serving eNodeB nodes 140 aand 140 c do not share an X2 interface.

In one or more embodiments, the MME 160 can further require that thenearest network element also include a function for bridging across thenetwork element without the need for a transcoding process. Byeliminating a transcoding process, the shortened RTP bearer path reducesthe processing complexity while increasing speed and throughput.Returning to the prior examples, where UE1 110 a enters into a callingsession with UE2 110 b, the MME 160 can determine that the eNodeB node140 a is the nearest network element to the two devices. Further, theMME 160 can determine that the eNodeB node 140 a includes a bridgingfunction to route the IP data packets from each of the end user devices110 a and 110 b to the other of the end user devices 110 a and 110 b.Therefore, the MME 160 can conclude that the eNobeB node 140 a is thenearest network element with a bridging function and can be used forenabling the shortest RTP bearer pathway 124 for the calling sessionincluding devices 110 a and 110 b. Similarly, the MME 160 can determinethat the nearest network device with bridging capability for a callingsession, between UE2 110 b and UE4 110 d, is the X2 interface betweenthe eNodeB node 140 a and the eNodeB node 140 b. Enabling the X2interface will activate a shortest RTP bearer path 126. In one or moreembodiments, transcoder-free operation can improve voice quality whileusing fewer network resources and elements.

For a calling session between UE2 110 b and UE3 110 c, the nearestnetwork element can be identified by the MME 160 as the wireless LAN125, which can serve as a bridging function to activate a shortest RTPbearer path 122. Where the calling session comprises UE4 110 d and UE5110 e, then the nearest network element is S-GW 170. However, S-GW 170does not include a bridging function. Therefore, the MME 160 candetermine that the nearest network element for the UE4 110 d and UE5 110e is actually P-GW 175, which has a transcode free bridging function.Activation of the bridging function in P-GW 175 can cause a shortest RTPbearer path 128.

In one or more embodiments, after the MME 160 has determined theshortest RTP bearer path for a pair for devices 110 a-e engaged in acommon caller session, then the MME 160 can notify network elements,such eNodeB 140 a-c, the wireless LAN 125, S-GW 170, P-GW 175. The MME160 can also notify end user devices 110 a-e. In addition tonotification, the MME 160 can direct the configuration of networkelements to cause the shortest RTP bearer path to become activated whilefreeing up other network resources that would be required to maintainthe default RTP bearer path. In one or more embodiments, the networkelements that are bypassed, due to the activation of the shortest RTPbearer path, can be directed to release resources previously allocatedto supporting either or both of the calling end user devices 110 a-b.These resources can be reallocated to other uses that can further speedup the communication system.

In one or more embodiments, where the MME 160 enables a shortest RTPbearer over the wireless LAN 125, the MME 160 can coordinate and/ordirect the wireless LAN 125 to establish a direct tunnel between the UE2110 b and UE3 110 c devices using the bridging function. As a result,the two mobile devices 110 b-c can exchange adaptive multi-rate (AMR)packets via the direct tunnel provided by the LAN 125. The two mobiledevices 110 b-110 c can, in turn, exchange SIP messages to establish themedia for the calling session (i.e, voice bearer). The two mobiledevices 110 b-c can continue to send regular SIP messages to the network105, with an appropriate indication that no resources are demanded fromthe network 105, as in a normal VoLTE, so that the signaling process canbe completed in the network 105.

In one or more embodiments, where the MME 160 enables a shortest RTPbearer over the eNodeB node 140 a for end user devices 110 a-b, then theMME 160 can coordinate and/or direct the eNodeB node 140 a to establisha direct tunnel between the UE1 110 a and UE2 110 b devices using thebridging function. As a result, modification in messages can be directedby the MME 160 to avoid using any resources in the transcode controllerand the GTP. For example, the MME 160 can direct changes to the AAR,RAR, and RAA messages that are associated with the P-CSCF, the PCRF 180,and the P-GW 175, the Create Bearer Request and Create Bearer Responseassociated with the P-GW 175, the S-GW 170, and the MME 160, the S1E-RAB Setup Request, S1 E-RAB Setup Response, and S1 UL NAS associatedwith the S1 interface, and the Transport RRC Connection ReconfigurationComplete and RRC UL Info Transfer message. In one or more embodiments,the MME 160 can direct the transmission of the RRC ConnectionReconfiguration message to the calling and called mobile devices 110b-c, separately, to invoke radio bearer set ups. The eNodeB node 140 a“bridges” the radio bearers for the two mobile devices 110 b-c so themedia tunnel is established. The two mobile devices 110 b-c can thenexchange AMR packets via the dedicated tunnel.

In one or more embodiments, where the MME 160 enables the shortest RTPbearer path using the X2 interface between eNodeB nodes 140 a and 140 b,then the MME 160 can coordinate and/or direct the X2 interface toestablish a direct tunnel between the UE2 110 b and UE4 110 c devices.As a result, modification in messages can be directed by the MME 160 toavoid using any resources in the transcode controller and the GTP. Forexample, the MME 160 can direct changes to the AAR, RAR, and RAAmessages that are associated with the P-CSCF, the PCRF 180, and the P-GW175, the Create Bearer Request and Create Bearer Response associatedwith the P-GW 175, the S-GW 170, and the MME 160, the S1 E-RAB SetupRequest, S1 E-RAB Setup Response, and S1 UL NAS associated with the S1interface, and the Transport RRC Connection Reconfiguration Complete andRRC UL Info Transfer message. In one or more embodiments, the MME 160can direct the transmission of the RRC Connection Reconfigurationmessage to the calling and called mobile devices 110 b and 110 d,separately, to invoke radio bearer set ups. The two eNodeB nodes 140 aand 140 b need to have functions to “bridge” the X2 interface betweenthe two eNodeB nodes 140 a and 140 b and the radio bearers for the twocall session devices 110 b and 110 d, so the media tunnel isestablished. The two mobile devices 110 b and 110 d can then exchangeAMR packets via the dedicated tunnel.

In one or more embodiments, where the MME 160 enables the shortest RTPbearer path over the GTP at the P-GW 175, then the MME 160 cancoordinate and/or direct the X2 interface to establish a direct tunnelbetween the UE2 110 b and UE4 110 c devices. As a result, modificationin messages can be directed by the MME 160 to avoid using at least someof the resources in the transcode controller and the GTP. For example,the MME 160 can direct changes to the AAR, RAR, and RAA messages thatare associated with the P-CSCF, the PCRF 180, and the P-GW 175. The MME160 can establish two, dedicated EPS bearers, one for the calling device110 b and one for the called device 110 e. The P-GW 175 needs to have afunction to “bridge” the X2 interface between the calling sessiondevices 110 b and 110 e so that the media tunnel is established. The twomobile devices 110 b and 110 e can then exchange AMR packets via thededicated tunnel.

In one or more embodiments, a wireless local area network (LAN) 125 canbe present at a service. The LAN 125 can be designed to provide wirelessaccess to the Internet 135 for devices 110 a-e that can be coupled tothe LAN 125. For example, the LAN 125 can be located at a public place,such as shopping mall, a college campus, a large church, an airport, acommercial location, or a sporting venue. In one embodiment, the LAN 125can provide access freely to devices 110 a-e with or withoutauthenticating access. For example, the LAN 125 can require that eachdevice 110 a-e enter a name and/or password to authorize access. In oneembodiment, access to the LAN 125 can be limited to devices 110 a and/orsubscribers associated with the LTE network 105. The LTE serviceprovider can provide and/or partner with a provider to make sure thatwireless LAN capability is available to its subscribers and/orsubscribed devices 110 a-e at specific locations. In another embodiment,access to the LAN 125 can be protected via a machine code or identifieror by a digital certificate. This approach can provide limited access toLAN 125 to protect the bandwidth of the LAN 125 while notinconveniencing a user of an end user device 110 a with a need to enterauthenticating information when activating a connection to the LAN 125.In another embodiment, the LAN 125 can be open for access to anywireless device without a protective password. For example, a publicbuilding can offer free, wireless access to the Internet 135 via awireless LAN 125 as an enticement for people to visit.

In one or more embodiments, end user devices 110 b-c can be coupled tothe wireless LAN 125 and to the cellular network 105. During normaloperation, an end user device 110 a will normally be connected to thecellular network 105 to which the device 110 a is subscribed, assumingthat the cellular network 105 is available at the location.

In one or more embodiments, the cellular network can determine alocation for each device 110 a. For example, the device 110 a can reporta location based on an on-board global positioning system (GPS)function. The cellular network 105 can determine if the end user device110 a is located in an area with good coverage from the wireless LAN 125and the cellular network E-UTRAN 120. Generally, the end user device 110a should not only have excellent coverage and signal strength but shouldbe able to maintain these levels if the end user device 110 a is moved anominal distance.

In one or more embodiments, the cellular network 105 can determine ifthe end user device 110 a is moving and, if moving, then it can furtherdetermine a direction and speed of movement. For example, the end userdevice 110 a can report a series of locations and timestamps to thecellular network 105. The locations and timestamps can be converted intomovement information. Alternatively, the end user device 110 a canconvert location information directly into movement information andreport the movement information to the cellular network 105.

In one or more embodiments, the MME 160 can alter a shortest bearer pathrouting after this routing has been established for a calling session.For example, during a calling session, the MME 160 can determine thatone of the end-user devices 110 a has moved during the call. The MME 160can detect this movement via, for example, reporting of locationinformation from the end-user device 110 a during the session. Inanother example, the MME 160 can determine that a device 110 a has movedbased on changes in signal strength or based on a device 110 a movingout of an eNobeB area. In one embodiment, the MME 160 can detect achange in performance of an element in the shortest bearer path. Forexample, a bridging communication link that is used to connect the datapaths of the end-user devices 110 a-b can malfunction and/or exhibitreliability issues. The MME 16 can detect these changes and/orunexpected aspects in performance and re-route the shortest bearer pathto the best available shortest bearer path that removes of mitigates theproblematic connection.

In one or more embodiments, the MME 160 can access a “T” function at asignal path device to allow for bridging of calling sessions involvingmultiple end-user calling devices 110 a-e. The function can allow forconference calling and for monitoring (CALEA) of the conference callusing shortest bearer path routing a point of the core network.

FIG. 2 depicts an illustrative embodiment of a method for providingshortest bearer paths for carrying internet protocol packets duringcalling sessions. Method 200 can begin at 204, where a calling mobiledevice, such as UE1 110 a, sends calling message for a calling sessioninvolving the calling device 110 a and a called device, such as UE2 110b, to a MME 160 of a Long-Term Evolution (LTE) communication network. Instep 208, the MME 160 can retrieve information on calling and calledmobile devices 110 a-b.

In step 212, the MME 160 can identify a “normal” Real-time TransportProtocol (RTP) bearer path for carrying IP packets through LTEcommunications network. In step 216, the MME 160 can compare informationon calling and called mobile devices 110 a-b to criteria forprovisioning of shortest RTP bearer path. In one or more embodiments,the MME 160 can retrieve network information associated with the callingand called end user devices 110 a-b. The MME 160 can determine whichwhether both devices 110 a-b are part of a group that is serviced by theMME 160. Alternatively, the MME 160 can determine whether both devices110 a-b are part of the same service area for the P-GW 175. In oneembodiment, this is the minimum requirement for the method to select andenable the shortest RTP bearer path. In another embodiment, the MME 160can verify that the both of the end user devices 110 a-b are registeredto the service provider of the communication system 100 as aprerequisite for using the shortest RTP bearer path. In anotherembodiment, the MME 160 can determine from the network information thatboth of the end user devices 110 a-b are intended or are likely toremain in the same MME group and/or P-GW group. In step 220, the MME 160can determine if the requirements for the provisioning of a shortest RTPbearer path have been met and, if met, then, in step 224, the MME 160can determine LTE network elements 140 a, 170, 175 that arecommunicatively coupled to the first and second mobile devices 110 a-band nearest to the first and second mobile devices 110 a-b. In one ormore embodiments, transcoder-free operation can improve voice qualitywhile using fewer network resources and elements

In one or more embodiments, the MME 160 can determine a nearest networkelement that can support a shortest RTP bearer path, one that is shorterthan the default bearer path. To determine the nearest element, the MME160 can use the network information for the calling and called end userdevices 110 a-b to first determine all of the network elements that arecommunicatively coupled to each of these end user devices 110 a-b.

In step 228, the MME 160 can determine the nearest network element 140 aof the communicatively coupled network elements 140, 170, 175, where thenearest network element also contains a bridging bearer function. In oneor more embodiments, the MME 160 can further require that the nearestnetwork element also include a function for bridging across the networkelement without the need for a transcoding process. By eliminating atranscoding process, the shortened RTP bearer path reduces theprocessing complexity while increasing speed and throughput. In step232, the MME 160 can identify a nearest network element 140 a and, onceidentified, then in step 236, the MME 160 can activate the bridgingbearer to generate a direct tunnel for IP packets of call session and tomodify the RTP bearer path to the shortest RTP bearer path 124. In step240, the call session between the two end user devices 110 a-b isconducted using an RTP bearer path.

FIG. 3 depicts an illustrative embodiment of the cellular system foraccessing additional communication resources and using these resourcesto share network resources between multiple mobile devices.Communication system 300 can be overlaid or operably coupled withsystems 100 of FIG. 1 as another representative embodiment ofcommunication system 100. System 300 allows for selecting an anchoreddevice 110 a that can route, though the wireless and cellular interfacesof the anchored device 110 a, cellular communications for user devices110 b-d and the cellular network 105.

Communication system 300 can comprise a Home Subscriber Server (HSS)340, a tElephone NUmber Mapping (ENUM) server 330, and other networkelements of an IMS network 350. The HSS 155 can receive subscriptioninformation 345, such as from PCRF 180 of FIG. 1). The subscriptioninformation 345 can be stored and used for a session event reportingregistration process for subscribing devices (e.g., application servers317 selectively requesting ULI). In one embodiment, the HSS 155 canreport ULI, such as by querying PCRF, which will report upon detectionof session events identified in subscription information while notreporting other ULI for session events that are not identified insubscription events.

The IMS network 350 can establish communications between IMS-compliantcommunication devices (CDs) 301, 302, Public Switched Telephone Network(PSTN) CDs 303, 305, and combinations thereof by way of a Media GatewayControl Function (MGCF) 320 coupled to a PSTN network 360. The MGCF 320need not be used when a communication session involves IMS CD to IMS CDcommunications. A communication session involving at least one PSTN CDmay utilize the MGCF 320.

IMS CDs 301, 302 can register with the IMS network 350 by contacting aProxy Call Session Control Function (P-CSCF), through a Session BorderController (SBC), which communicates with an interrogating CSCF(I-CSCF), which in turn, communicates with a Serving CSCF (S-CSCF) toregister the CDs with the HSS 155. To initiate a communication sessionbetween CDs, an originating IMS CD 301 can submit a Session InitiationProtocol (SIP INVITE) message to the SBC 313. The SBC 313 can forwardthe SIP INVITE to an originating P-CSCF 304, which communicates with acorresponding originating S-CSCF 306. Without some form of bearer pathshorting, the SBC 313 serves as the anchor point for all voice over LTEcalls. For example, if end-user device 110 a calls end-user device 110b, then the normal RTP path is UE1 110 a to SBC 313 to UE2 110 b. In oneembodiment, re-routing the data communications via a shortest RTP bearerpath avoids all calls being anchored at the SBC 313.

The originating S-CSCF 306 can submit the SIP INVITE message to one ormore application servers 317 that can provide a variety of services toIMS subscribers. For example, the application servers 317 can be usedfor various functions including billing and/or network performanceanalysis. In one embodiment, the application servers 317 can be used toperform originating call feature treatment functions on the callingparty number received by the originating S-CSCF 306 in the SIP INVITEmessage. Originating treatment functions can include determining whetherthe calling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 306 can submit queries to the ENUMsystem 330 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 307 to submit a query to the HSS 340 toidentify a terminating S-CSCF 314 associated with a terminating IMS CDsuch as reference 302. Once identified, the I-CSCF 307 can submit theSIP INVITE message to the terminating S-CSCF 314. The terminating S-CSCF314 can then identify a terminating P-CSCF 316 associated with theterminating CD 302. The P-CSCF 316 may then signal the CD 302 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 3 may be interchangeable. It is further noted that communicationsystem 300 can be adapted to support video conferencing. In addition,communication system 300 can be adapted to provide the IMS CDs 301, 302with multimedia and Internet services.

If the terminating communication device is instead a PSTN CD such as CD303 or CD 305 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 330 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 306 to forward the call to the MGCF 320 via a Breakout GatewayControl Function (BGCF) 319. The MGCF 320 can then initiate the call tothe terminating PSTN CD over the PSTN network 360 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 3 can operate as wirelineor wireless devices. For example, the CDs of FIG. 3 can becommunicatively coupled to a cellular base station 321, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 350 of FIG. 3. The cellular accessbase station 321 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 3.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 321 may communicate directly with the IMS network 350 as shownby the arrow connecting the cellular base station 321 and the P-CSCF316.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

Application servers 317 can be adapted to perform function 371 (e.g.,via software executed at the application server) which can includesubscribing to session events for selective reporting of ULI. As anexample, the application server 317 can subscribe to the PCC (e.g., PCRF180) which allows the application server 317 to selectively receive ULIbased on events that are pertinent to the functions being performed bythe application server without receiving unnecessary ULI for events thatare not pertinent to the functions being performed by the AF. Forinstance, an application server 317 that is performing location-basedservice authorization can subscribe to session initiation events andsession updates caused by user mobility while not subscribing to sessionterminations. In this example, the application server 317 can monitorthe location of the UE based on the ULI to enforce authorization oflocation-based services in only a particular area. The subscribingfunction 371 performed by the application server 317 can result indistribution of the subscription information 345 to devices that arepart of the ULI reporting process, such as HSS 155 or an MME (notshown).

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as ^(3rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 4 depicts an illustrative embodiment of a communication device thatcan be used in achieving improved network access via an anchored device.Communication device 400 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and 3,including application servers, PCEF devices, PCRF devices, UEs, HSS, MMEand so forth. Device 400 can be a server that performs policy controland charging functions in a mobile communications network. Device 400can receive subscriptions from a subset of application servers of aplurality of application servers, where the subscriptions identifysession events of a communication session for which the subset ofapplication servers request user location information, or a subset ofthe triggering events are subscribed. Device 400 can providesubscription information based on the subscriptions to core networknodes of the mobile communications network. Device 400 can receive userlocation information from the core network nodes responsive to detectionof triggering events corresponding to the session events of thesubscriptions. Device 400 can provide the user location information toan IP multimedia subsystem network for delivery to the subset ofapplication servers without delivery to remaining application servers ofthe plurality of application servers that did not subscribe to thesession events, or without delivering the ULI for undesired subsequenttriggering events.

To enable selective reporting of ULI via a subscriber registrationprocess, communication device 400 can comprise various components suchas one or more of a wireline and/or wireless transceiver 402 (hereintransceiver 402), a user interface (UI) 404, a power supply 414, alocation receiver 416, a motion sensor 418, an orientation sensor 420,and a controller 406 for managing operations thereof. The transceiver402 can support short-range or long-range wireless access technologiessuch as Bluetooth, ZigBee, WiFi, DECT, or cellular communicationtechnologies, just to mention a few. Cellular technologies can include,for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX,SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 402 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 404 can include a depressible or touch-sensitive keypad 408 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device400. The keypad 408 can be an integral part of a housing assembly of thecommunication device 400 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth. The keypad 408 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 404 can further include a display410 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 400. In anembodiment where the display 410 is touch-sensitive, a portion or all ofthe keypad 408 can be presented by way of the display 410 withnavigation features.

The display 410 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 400 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 410 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 410 can be an integral part of thehousing assembly of the communication device 400 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 404 can also include an audio system 412 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 412 can further include amicrophone for receiving audible signals of an end user. The audiosystem 412 can also be used for voice recognition applications. The UI404 can further include an image sensor 413 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 414 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 400 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 416 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 400 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 418can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 400 in three-dimensional space. Theorientation sensor 420 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device400 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 400 can use the transceiver 402 to alsodetermine a proximity to a cellular, WiFi, Bluetooth, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 406 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 400.

Other components not shown in FIG. 4 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 400 can include a reset button (not shown). The reset button canbe used to reset the controller 406 of the communication device 400. Inyet another embodiment, the communication device 400 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 400 to force thecommunication device 400 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 400 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 400 as described herein can operate with moreor less of the circuit components shown in FIG. 4. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 400 shown in FIG. 4 or portions thereof canserve as a representation of one or more of the devices of systems 100and/or 300 of FIGS. 1 and 3. In addition, the controller 406 can beadapted in various embodiments to perform the functions 371 to enable asubscriber registration process that distributes subscriptioninformation so that ULI is selectively reported based on particulardetected session events that are pertinent to the functions of thesubscribing device, such as ULI being reported for session terminationevents to an application server performing network performance analysis.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as a PCC (e.g., the PCRF 180 and/or the PCEF 220),an MME, an HSS, an application server, a UE and other devices of FIGS.1-2 and 5-6 to enable selective ULI reporting based on a subscriptionprocess. For example, the machine can receive a subscription from anapplication server, where the machine performs policy control andcharging functions in a mobile communications network, and where thesubscription identifies a session event occurring in a communicationsession for which the application server requests user locationinformation. The machine can provide subscription information based onthe subscription to core network nodes of the mobile communicationsnetwork. The machine can receive user location information from the corenetwork nodes responsive to a detection of a triggering eventcorresponding to the session event of the subscription. The machine canprovide the user location information to an IP multimedia subsystemnetwork for delivery to the application server, where the delivery ofthe user location information is limited to application servers that aresubscribed to the session event, and/or only for the event/sub-event anapplication server has subscribed.

In some embodiments, the machine may be connected (e.g., using a network526) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine inserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 500 may include a processor (or controller) 502(e.g., a central processing unit (CPU), a graphics processing unit (GPU,or both), a main memory 504 and a static memory 506, which communicatewith each other via a bus 508. The computer system 500 may furtherinclude a display unit 510 (e.g., a liquid crystal display (LCD), a flatpanel, or a solid state display. The computer system 500 may include aninput device 512 (e.g., a keyboard), a cursor control device 514 (e.g.,a mouse), a disk drive unit 516, a signal generation device 518 (e.g., aspeaker or remote control) and a network interface device 520. Indistributed environments, the embodiments described in the subjectdisclosure can be adapted to utilize multiple display units 510controlled by two or more computer systems 500. In this configuration,presentations described by the subject disclosure may in part be shownin a first of the display units 510, while the remaining portion ispresented in a second of the display units 510.

The disk drive unit 516 may include a tangible computer-readable storagemedium 522 on which is stored one or more sets of instructions (e.g.,software 524) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 524 may also reside, completely or at least partially,within the main memory 504, the static memory 506, and/or within theprocessor 502 during execution thereof by the computer system 500. Themain memory 504 and the processor 502 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices that can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. It is furthernoted that a computing device such as a processor, a controller, a statemachine or other suitable device for executing instructions to performoperations or methods may perform such operations directly or indirectlyby way of one or more intermediate devices directed by the computingdevice.

While the tangible computer-readable storage medium 522 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth, WiFi, Zigbee), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 500.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

The exemplary embodiments described herein can be part of variouscommunication systems including an Internet Protocol Television (IPTV)media system satellite and/or terrestrial communication systems. Thesesystems can provide various services including voice video and/or dataservices. Multiple forms of media services can be offered to mediadevices (e.g., mobile communication devices, set top boxes, desk topcomputers, and so forth) over landline technologies. Additionally, mediaservices can be offered to media devices by way of wireless technologiessuch as through use of a wireless access base station operatingaccording to common wireless access protocols such as Global System forMobile or GSM, Code Division Multiple Access or CDMA, Time DivisionMultiple Access or TDMA, Universal Mobile Telecommunications or UMTS,World interoperability for Microwave or WiMAX, Software Defined Radio orSDR, Long Term Evolution or LTE, and so on. Other present and nextgeneration wide area wireless access network technologies can be used inone or more embodiments of the subject disclosure.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,can be used in the subject disclosure. In one or more embodiments,features that are positively recited can also be excluded from theembodiment with or without replacement by another component or step. Thesteps or functions described with respect to the exemplary processes ormethods can be performed in any order. The steps or functions describedwith respect to the exemplary processes or methods can be performedalone or in combination with other steps or functions (from otherembodiments or from other steps that have not been described). Less thanall of the steps or functions described with respect to the exemplaryprocesses or methods can also be performed in one or more of theexemplary embodiments. Further, the use of numerical terms to describe adevice, component, step or function, such as first, second, third, andso forth, is not intended to describe an order or function unlessexpressly stated so. The use of the terms first, second, third and soforth, is generally to distinguish between devices, components, steps orfunctions unless expressly stated otherwise. Additionally, one or moredevices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A device, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, comprising: receiving a calling message indicating a callingsession between a first mobile device and a second mobile device;retrieving first network information associated with the first mobiledevice and second network information associated with the second mobiledevice according to the calling message; identifying a first rate ofmovement of the first mobile device according to the first networkinformation and identifying a second rate of movement of the secondmobile device according to the second network information; determiningwhether the calling session qualifies for shortening of a bearer pathaccording to the first rate of movement of the first mobile device andthe second rate of movement of the second mobile device being less thana threshold, wherein the shortening reduces a number of requiredelements in the bearer path; comparing the first network information andthe second network information to criteria for provisioning a targetshortened bearer path resulting in a comparison; determining that thefirst mobile device and the second mobile device are to remain in a samemobility management entity group according to the first rate ofmovement, the second rate of movement and the comparison; and activatingthe target shortened bearer path for carrying internet protocol packetsassociated with the calling session.
 2. The device of claim 1, whereinthe operations comprise identifying the bearer path through acommunication network for carrying internet protocol packets. associatedwith the calling session according to the first network information andthe second network information.
 3. The device of claim 1, wherein theoperations comprise identifying a base station communicatively coupledto both the first mobile device and second mobile device, andcommunicatively coupled to a cellular network.
 4. The device of claim 1,wherein the operations comprise identifying a wireless local areanetwork (LAN) access point communicatively coupled to both the firstmobile device and second mobile device, and communicatively coupled to awireless LAN.
 5. The device of claim 1, wherein the operations compriseselecting a network element that is communicatively coupled to both thefirst mobile device and the second mobile device and that is closest tothe first mobile device and the second mobile device to identify anearest network element according to the calling session qualifying forbearer path shortening.
 6. The device of claim 1, wherein a wireless LANaccess point is selected as a network element in the targeted shortenedbearer path based on the wireless LAN access point using less systemresources than a base station for communication between the first mobiledevice and the second mobile device.
 7. The device of claim 1, whereinthe operations comprise determining if a nearest network elementcomprises a transcoder-free bridging bearer path.
 8. The device of claim1, wherein the operations comprise identifying that the first mobiledevice and the second mobile device have a common coder-decoder (CODEC).9. The device of claim 8, wherein the activating of the target shortenedbearer path comprises activating a transcoder-free target shortenedbearer path responsive to identifying the common CODEC to generate adirect tunnel for carrying the internet protocol packets associated withthe calling session and to modify the bearer path to the transcoder-freetarget shortened bearer path.
 10. A machine-readable storage medium,comprising executable instructions that, when executed by a processingsystem including a processor, facilitate performance of operations,comprising: obtaining a message indicating a communication sessionbetween a first mobile device and a second mobile device; receivingfirst network information associated with the first mobile device andsecond network information associated with the second mobile deviceaccording to the message; identifying a first rate of movement of thefirst mobile device according to the first network information andidentifying a second rate of movement of the second mobile deviceaccording to the second network information; determining whether thecommunication session qualifies for shortening of a bearer pathaccording to the first rate of movement of the first mobile device andthe second rate of movement of the second mobile device being less thana threshold, wherein the shortening reduces a number of requiredelements in the bearer path; comparing the first network information andthe second network information to criteria for provisioning a targetshortened bearer path resulting in a comparison; determining that thefirst mobile device and the second mobile device are to remain in a samemobility management entity group according to the first rate ofmovement, the second rate of movement and the comparison; identifyingthat the first mobile device and the second mobile device have a commoncoder-decoder (CODEC); and activating the target shortened bearer pathfor carrying internet protocol packets associated with the communicationsession responsive to identifying the common CODEC to generate a directtunnel for carrying the internet protocol packets associated with thecommunication session and to modify the bearer path to the targetshortened bearer path.
 11. The machine-readable storage medium of claim10, wherein the operations further comprise identifying the bearer paththrough a communication network for carrying internet protocol packets.12. The machine-readable storage medium of claim 10, wherein theoperations comprise identifying a base station communicatively coupledto both the first mobile device and second mobile device, andcommunicatively coupled to a cellular network.
 13. The machine-readablestorage medium of claim 10, wherein the operations comprise identifyinga wireless local area network (LAN) access point communicatively coupledto both the first mobile device and second mobile device, andcommunicatively coupled to a wireless LAN.
 14. The machine-readablestorage medium of claim 10, wherein the operations comprise selecting anetwork element that is communicatively coupled to both the first mobiledevice and the second mobile device and that is closest to the firstmobile device and the second mobile device to identify a nearest networkelement according to the communication session qualifying for bearerpath shortening.
 15. The machine-readable storage medium of claim 10,wherein a wireless LAN access point is selected as a network elementbased on the wireless LAN access point using less system resources thana base station for communication between the first mobile device and thesecond mobile device.
 16. The machine-readable storage medium of claim10, determining if a nearest network element comprises a transcoder-freetarget shortened bearer path.
 17. A method, comprising: receiving, by aprocessing system including a processor, a calling message indicating acalling session between a first mobile device and a second mobiledevice; retrieving, by the processing system, first network informationassociated with the first mobile device and second network informationassociated with the second mobile device according to the callingmessage; identifying, by the processing system, a first rate of movementof the first mobile device according to the first network informationand identifying, by the processing system, a second rate of movement ofthe second mobile device according to the second network information;determining, by the processing system, whether the calling sessionqualifies for shortening of a bearer path according to the first rate ofmovement of the first mobile device and the second rate of movement ofthe second mobile device being less than a threshold, wherein theshortening reduces a number of required elements in the bearer path;comparing, by the processing system, the first network information andthe second network information to criteria for provisioning a targetshortened bearer path resulting in a comparison; determining, by theprocessing system, that the first mobile device and the second mobiledevice are to remain in a same mobility management entity groupaccording to the first rate of movement, the second rate of movement andthe comparison; identifying, by the processing system, a wireless localarea network (LAN) access point communicatively coupled to both thefirst mobile device and second mobile device, and communicativelycoupled to a wireless LAN; selecting, by the processing system, anetwork element that is communicatively coupled to both the first mobiledevice and the second mobile device and that is closest to the firstmobile device and the second mobile device to identify a nearest networkelement according to the calling session qualifying for transcoder-freebearer path shortening, wherein the wireless LAN access point isselected as the network element based on the wireless LAN access pointusing less system resources than a base station for communicationbetween the first mobile device and the second mobile device; andactivating, by the processing system, the target shortened bearer pathfor carrying internet protocol packets associated with the callingsession.
 18. The method of claim 17, comprising identifying, by theprocessing system, the bearer path through a communication network forcarrying internet protocol packets.
 19. The method of claim 17,comprising identifying, by the processing system, that the first mobiledevice and the second mobile device have a common coder-decoder (CODEC).20. The method of claim 19, wherein the activating of the targetshortened bearer path comprises activating, by the processing system, atranscoder-free target shortened bearer path responsive to identifyingthe common CODEC to generate a direct tunnel for carrying the internetprotocol packets associated with the calling session and to modify thebearer path to the transcoder-free target shortened bearer path.